Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 48f0fe53dedf3b431cce45dbb57a8e7ce30de26efb67a57eeca6d19d07ea8c68

Tx prefix hash: b10e508a5607d55fe3d76ca392ba9013c4d45ea95b4a935d1ec5a43f28667910
Tx public key: 6f168300d6e3a0983a65b23c631d324e9b5fe3b4b7ddb69da0dbc3b9d0ce6ec7
Timestamp: 1639054265 Timestamp [UCT]: 2021-12-09 12:51:05 Age [y:d:h:m:s]: 03:188:15:27:56
Block: 391785 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 913499 RingCT/type: yes/0
Extra: 016f168300d6e3a0983a65b23c631d324e9b5fe3b4b7ddb69da0dbc3b9d0ce6ec702110000000306faf294000000000000000000

1 output(s) for total of 30.892568673000 dcy

stealth address amount amount idx
00: 10493834804ef2d0457c8847c96f6712fee169975ec343e5dc17d1737e7ab269 30.892568673000 788366 of 0

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": 391795, "vin": [ { "gen": { "height": 391785 } } ], "vout": [ { "amount": 30892568673, "target": { "key": "10493834804ef2d0457c8847c96f6712fee169975ec343e5dc17d1737e7ab269" } } ], "extra": [ 1, 111, 22, 131, 0, 214, 227, 160, 152, 58, 101, 178, 60, 99, 29, 50, 78, 155, 95, 227, 180, 183, 221, 182, 157, 160, 219, 195, 185, 208, 206, 110, 199, 2, 17, 0, 0, 0, 3, 6, 250, 242, 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