Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 92b9917b2042f1493a564326b411ba4ccb2bf4bc98dd7aa1073419fb27c2cd36

Tx prefix hash: be8f191c8885b7b8a7f65e848cbd86ebc601fe530e5d1b61c5c4b47f5610c3ab
Tx public key: 02ef55230e66488ac7984a557d805c0f136b7b75e69bc4e4b3a6295ece079d26
Timestamp: 1585550327 Timestamp [UCT]: 2020-03-30 06:38:47 Age [y:d:h:m:s]: 04:274:09:50:51
Block: 89829 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1095298 RingCT/type: yes/0
Extra: 0102ef55230e66488ac7984a557d805c0f136b7b75e69bc4e4b3a6295ece079d2602110000003345705818000000000000000000

1 output(s) for total of 309.285819741000 dcy

stealth address amount amount idx
00: c9e19ba90cf7b24bb7e957f2f2619f31319e952c6939175a212f6ad9b4f2206d 309.285819741000 161003 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": 89839, "vin": [ { "gen": { "height": 89829 } } ], "vout": [ { "amount": 309285819741, "target": { "key": "c9e19ba90cf7b24bb7e957f2f2619f31319e952c6939175a212f6ad9b4f2206d" } } ], "extra": [ 1, 2, 239, 85, 35, 14, 102, 72, 138, 199, 152, 74, 85, 125, 128, 92, 15, 19, 107, 123, 117, 230, 155, 196, 228, 179, 166, 41, 94, 206, 7, 157, 38, 2, 17, 0, 0, 0, 51, 69, 112, 88, 24, 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