Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: c9a386b3f4239d4c470b3837465a5b1dbcc5008f59d6aa8e836a334f89395c4b

Tx prefix hash: 002333653c3c32998cf338004079f9059ee8e5b270de3ed84d2f78caba7e73a1
Tx public key: 06f79e43e03591c31ac48e0c65db0de6732f56cda48f43927c4d5f61d025f279
Timestamp: 1736941303 Timestamp [UCT]: 2025-01-15 11:41:43 Age [y:d:h:m:s]: 00:310:14:09:04
Block: 1197851 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 219494 RingCT/type: yes/0
Extra: 0106f79e43e03591c31ac48e0c65db0de6732f56cda48f43927c4d5f61d025f2790211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8cfcf370ad3e9cf9d028e4633572e3e65fbc18b4c467f07a3f954bec4989a9e3 0.600000000000 1684468 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1197861, "vin": [ { "gen": { "height": 1197851 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8cfcf370ad3e9cf9d028e4633572e3e65fbc18b4c467f07a3f954bec4989a9e3" } } ], "extra": [ 1, 6, 247, 158, 67, 224, 53, 145, 195, 26, 196, 142, 12, 101, 219, 13, 230, 115, 47, 86, 205, 164, 143, 67, 146, 124, 77, 95, 97, 208, 37, 242, 121, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8