Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9b9c8de20128366f53f81ff75b62931640ad3c29826ab911298d14b572af2519

Tx prefix hash: bb7edfdd02c1bdbb9e91313e13f0861108702ff9a7b1b79dc791b7cebc0ede63
Tx public key: e3b18c43ed67c1d2094a37a405b692d0c00dd96d52e783ac07e923c0c9de13c3
Timestamp: 1715979791 Timestamp [UCT]: 2024-05-17 21:03:11 Age [y:d:h:m:s]: 01:013:13:03:10
Block: 1024229 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 270610 RingCT/type: yes/0
Extra: 01e3b18c43ed67c1d2094a37a405b692d0c00dd96d52e783ac07e923c0c9de13c302110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9b510022e4b4e9e568f76375ef94847d41f82fbc20d740c68f73367d330acb43 0.600000000000 1489808 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": 1024239, "vin": [ { "gen": { "height": 1024229 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9b510022e4b4e9e568f76375ef94847d41f82fbc20d740c68f73367d330acb43" } } ], "extra": [ 1, 227, 177, 140, 67, 237, 103, 193, 210, 9, 74, 55, 164, 5, 182, 146, 208, 192, 13, 217, 109, 82, 231, 131, 172, 7, 233, 35, 192, 201, 222, 19, 195, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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