Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f57b5796a91717e9d618477cf874187b9487cc5495ae9d2016948b88af0fe59

Tx prefix hash: 7f36f39dc912e009a1a91f182a4a31b5d3ed664c561e2bc5e8946ceb866fdda5
Tx public key: d5aaf9da1c9408fe3758b478f092e500016c6ead06ef3017967fe46d798f2f3d
Timestamp: 1728788237 Timestamp [UCT]: 2024-10-13 02:57:17 Age [y:d:h:m:s]: 00:172:20:24:48
Block: 1130414 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 123318 RingCT/type: yes/0
Extra: 01d5aaf9da1c9408fe3758b478f092e500016c6ead06ef3017967fe46d798f2f3d021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a1514676d6b643a4c81ab2ec40f0bcf7ebcd4eabb0b9eaa27eb4d549d786516c 0.600000000000 1613291 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": 1130424, "vin": [ { "gen": { "height": 1130414 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a1514676d6b643a4c81ab2ec40f0bcf7ebcd4eabb0b9eaa27eb4d549d786516c" } } ], "extra": [ 1, 213, 170, 249, 218, 28, 148, 8, 254, 55, 88, 180, 120, 240, 146, 229, 0, 1, 108, 110, 173, 6, 239, 48, 23, 150, 127, 228, 109, 121, 143, 47, 61, 2, 17, 0, 0, 0, 1, 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