Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c74311b92ba0493e585b2a3ed336c87ab8a8cda81b7424345cb41d69c7af70fe

Tx prefix hash: b9fd9c5455becfc5a562a54b405b8c52ddcfeece0bbd9d411323114bbc789aa7
Tx public key: 9451ddf298a77c108e123831cc35a07d1dd8b7b05e485d9223bac5a3e0645bb0
Timestamp: 1724894274 Timestamp [UCT]: 2024-08-29 01:17:54 Age [y:d:h:m:s]: 00:243:02:04:42
Block: 1098131 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 173608 RingCT/type: yes/0
Extra: 019451ddf298a77c108e123831cc35a07d1dd8b7b05e485d9223bac5a3e0645bb002110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ef86e43a0fb7a71fabce1c65e3e10b9c0f995dc8b4c6bc52d9c55d3350257601 0.600000000000 1573742 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": 1098141, "vin": [ { "gen": { "height": 1098131 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ef86e43a0fb7a71fabce1c65e3e10b9c0f995dc8b4c6bc52d9c55d3350257601" } } ], "extra": [ 1, 148, 81, 221, 242, 152, 167, 124, 16, 142, 18, 56, 49, 204, 53, 160, 125, 29, 216, 183, 176, 94, 72, 93, 146, 35, 186, 197, 163, 224, 100, 91, 176, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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