Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a78396d1b0ffc617d105ce1fc057cd43666ef5492aa67d047e71c635e32cf49b

Tx prefix hash: 96881ed145667b782ab7518d285d27794d76418dc32429173df4761e562fd467
Tx public key: d4ad2bb86bb05bbff9bd7b521631aa057d9d9b65f1d48d6996146b3639731a2f
Timestamp: 1727206577 Timestamp [UCT]: 2024-09-24 19:36:17 Age [y:d:h:m:s]: 00:197:11:15:50
Block: 1117304 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 140947 RingCT/type: yes/0
Extra: 01d4ad2bb86bb05bbff9bd7b521631aa057d9d9b65f1d48d6996146b3639731a2f021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c580a06e8e9a8f99c8d633f5cb8f90555dc26064d938a24e40fdbfb79531f3ef 0.600000000000 1598093 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": 1117314, "vin": [ { "gen": { "height": 1117304 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c580a06e8e9a8f99c8d633f5cb8f90555dc26064d938a24e40fdbfb79531f3ef" } } ], "extra": [ 1, 212, 173, 43, 184, 107, 176, 91, 191, 249, 189, 123, 82, 22, 49, 170, 5, 125, 157, 155, 101, 241, 212, 141, 105, 150, 20, 107, 54, 57, 115, 26, 47, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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