Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 74205b8ebc2c158ce9e61f15115f0e9491f37e2d621ad8baf84fc3337d2af9dc

Tx prefix hash: 94051c9c6efa112ad8d8130c42c2006139af775dae7c3ed23a89e7df8fcb824a
Tx public key: 5bee3c6ac99f5a1cdb208625edf696cbc503a425564d4c7585d1294c972b0426
Timestamp: 1704289780 Timestamp [UCT]: 2024-01-03 13:49:40 Age [y:d:h:m:s]: 01:311:17:47:59
Block: 927321 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 481616 RingCT/type: yes/0
Extra: 015bee3c6ac99f5a1cdb208625edf696cbc503a425564d4c7585d1294c972b04260211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9275ea14d86a710060b4e31109c1f1507b98c01243330d3f153de76cc2dd9351 0.600000000000 1385157 of 15

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": 927331, "vin": [ { "gen": { "height": 927321 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9275ea14d86a710060b4e31109c1f1507b98c01243330d3f153de76cc2dd9351" } } ], "extra": [ 1, 91, 238, 60, 106, 201, 159, 90, 28, 219, 32, 134, 37, 237, 246, 150, 203, 197, 3, 164, 37, 86, 77, 76, 117, 133, 209, 41, 76, 151, 43, 4, 38, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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