Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5546160e57bd88c2f1a2828769ff78ebf759a18a729e313f28da71a5d5bfc049

Tx prefix hash: 9ca3286531410fb3cb909011b6a224c3c8274f61bb98ab3845a7f2d76fe98f4a
Tx public key: 485743d0f25bebc713122271541b8c5f15d9ad65196d60345944e4ff38caff2c
Timestamp: 1684366606 Timestamp [UCT]: 2023-05-17 23:36:46 Age [y:d:h:m:s]: 02:022:04:59:37
Block: 762388 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 538003 RingCT/type: yes/0
Extra: 01485743d0f25bebc713122271541b8c5f15d9ad65196d60345944e4ff38caff2c02110000000175e3f0e9000000000000000000

1 output(s) for total of 1.827646751000 dcy

stealth address amount amount idx
00: d193276c5807c436c99aa640b4e9a314cb01860868fa8e263697f09ef5c25d9e 1.827646751000 1211133 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": 762398, "vin": [ { "gen": { "height": 762388 } } ], "vout": [ { "amount": 1827646751, "target": { "key": "d193276c5807c436c99aa640b4e9a314cb01860868fa8e263697f09ef5c25d9e" } } ], "extra": [ 1, 72, 87, 67, 208, 242, 91, 235, 199, 19, 18, 34, 113, 84, 27, 140, 95, 21, 217, 173, 101, 25, 109, 96, 52, 89, 68, 228, 255, 56, 202, 255, 44, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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