Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf8205008fdc44f10f2f318894c30f3e6907b3528b676637bfe253cf594c5ba6

Tx prefix hash: 433ee7fc7c2ccc4fee45db039e43d0350b2662da83ba67a9a526bf7d4073c492
Tx public key: d386881d1abd25f60b44307a11ee3261d6bf190124410de0ded51f4b4e6e3804
Timestamp: 1617104352 Timestamp [UCT]: 2021-03-30 11:39:12 Age [y:d:h:m:s]: 03:271:08:04:09
Block: 229678 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 953410 RingCT/type: yes/0
Extra: 01d386881d1abd25f60b44307a11ee3261d6bf190124410de0ded51f4b4e6e3804021100000009ece3035d000000000000000000

1 output(s) for total of 106.409897339000 dcy

stealth address amount amount idx
00: 04cb8c807194d24ed44d8f70dc8fe8947a09919d5f6bf383a0014ddd428029fe 106.409897339000 476640 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": 229688, "vin": [ { "gen": { "height": 229678 } } ], "vout": [ { "amount": 106409897339, "target": { "key": "04cb8c807194d24ed44d8f70dc8fe8947a09919d5f6bf383a0014ddd428029fe" } } ], "extra": [ 1, 211, 134, 136, 29, 26, 189, 37, 246, 11, 68, 48, 122, 17, 238, 50, 97, 214, 191, 25, 1, 36, 65, 13, 224, 222, 213, 31, 75, 78, 110, 56, 4, 2, 17, 0, 0, 0, 9, 236, 227, 3, 93, 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