Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0bd2f84fa2e9d04e3e310472a82aa10d7bb7c3e49cd756521214f7aaa47bff82

Tx prefix hash: 4d4e36dbc73fe7a9e55d5527e5ba114738c95e8cde6c341a4580e8e9d66b9020
Tx public key: dd408a504e2efbfeb26ca2aeb721f00d8ffbbc9cda3384d59d2bd2696e51c374
Timestamp: 1579021854 Timestamp [UCT]: 2020-01-14 17:10:54 Age [y:d:h:m:s]: 05:080:01:49:44
Block: 45444 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1207444 RingCT/type: yes/0
Extra: 01dd408a504e2efbfeb26ca2aeb721f00d8ffbbc9cda3384d59d2bd2696e51c3740211000000242264afe6000000000000000000

1 output(s) for total of 433.948581326000 dcy

stealth address amount amount idx
00: a3167cb050641e55039097c558b9d8159792b72120f4ad37825d86ef60119c04 433.948581326000 83047 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": 45454, "vin": [ { "gen": { "height": 45444 } } ], "vout": [ { "amount": 433948581326, "target": { "key": "a3167cb050641e55039097c558b9d8159792b72120f4ad37825d86ef60119c04" } } ], "extra": [ 1, 221, 64, 138, 80, 78, 46, 251, 254, 178, 108, 162, 174, 183, 33, 240, 13, 143, 251, 188, 156, 218, 51, 132, 213, 157, 43, 210, 105, 110, 81, 195, 116, 2, 17, 0, 0, 0, 36, 34, 100, 175, 230, 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