Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 02bfe4cc6f6044e2724096d81a9c67262c59441e41ab1487f4edccfda9610d57

Tx prefix hash: 2e4d4cd6ca8b19c78613d77a556d9027a5a77161602100738db58bbd848acc43
Tx public key: bb4c5f79832b8d99f920e6afe1c91a0df4f6bb1e28646ba0976b07c596efe50a
Timestamp: 1638136907 Timestamp [UCT]: 2021-11-28 22:01:47 Age [y:d:h:m:s]: 03:153:17:46:38
Block: 384240 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 888572 RingCT/type: yes/0
Extra: 01bb4c5f79832b8d99f920e6afe1c91a0df4f6bb1e28646ba0976b07c596efe50a02110000000337cb3088000000000000000000

1 output(s) for total of 32.723047963000 dcy

stealth address amount amount idx
00: ec759a7a7838b9dd454ac2c3a78b11d97aa2fdd39f1d4f2dc37cfbb1e45d9aa9 32.723047963000 775601 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": 384250, "vin": [ { "gen": { "height": 384240 } } ], "vout": [ { "amount": 32723047963, "target": { "key": "ec759a7a7838b9dd454ac2c3a78b11d97aa2fdd39f1d4f2dc37cfbb1e45d9aa9" } } ], "extra": [ 1, 187, 76, 95, 121, 131, 43, 141, 153, 249, 32, 230, 175, 225, 201, 26, 13, 244, 246, 187, 30, 40, 100, 107, 160, 151, 107, 7, 197, 150, 239, 229, 10, 2, 17, 0, 0, 0, 3, 55, 203, 48, 136, 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