Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9c6482e67bf5aa5b52f2e1b62161f16c1b1251448ceaa921ed621144aa3a3fed

Tx prefix hash: 332d9ee18a0f625c984859ead769195684d79eb00e3e18591e8a5d9bcb08c7e5
Tx public key: d23005f38dd71274df14cef40c115d6ff9f35eea6eb583f55ed78f7ed30938d4
Timestamp: 1719566240 Timestamp [UCT]: 2024-06-28 09:17:20 Age [y:d:h:m:s]: 01:142:10:38:15
Block: 1053955 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 360359 RingCT/type: yes/0
Extra: 01d23005f38dd71274df14cef40c115d6ff9f35eea6eb583f55ed78f7ed30938d402110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 77ed54c22be46494775b6dbba658f060ae7c3a7cbe0ba8ecde9bccda56d7eb86 0.600000000000 1524310 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": 1053965, "vin": [ { "gen": { "height": 1053955 } } ], "vout": [ { "amount": 600000000, "target": { "key": "77ed54c22be46494775b6dbba658f060ae7c3a7cbe0ba8ecde9bccda56d7eb86" } } ], "extra": [ 1, 210, 48, 5, 243, 141, 215, 18, 116, 223, 20, 206, 244, 12, 17, 93, 111, 249, 243, 94, 234, 110, 181, 131, 245, 94, 215, 143, 126, 211, 9, 56, 212, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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