Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b04c6ef75e049544348a4224b580979b7845f581858d49ccf48e7b653f8e09ba

Tx prefix hash: a95dae000ca7caac35af37b98a72ed60e6b5ba0bb4e8d7f2f7dfb8cc1b13183e
Tx public key: 6ad5991fe7423559b6d85d1bdea80ab290a4a838cdb32f93fca29e9cc746308f
Timestamp: 1751845420 Timestamp [UCT]: 2025-07-06 23:43:40 Age [y:d:h:m:s]: 00:130:08:01:25
Block: 1320246 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 91563 RingCT/type: yes/0
Extra: 016ad5991fe7423559b6d85d1bdea80ab290a4a838cdb32f93fca29e9cc746308f02110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e076982e9fa9808fdc9b0c4c115da476fb993499d952bcaf80d5df12a7f89e70 0.600000000000 1807943 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": 1320256, "vin": [ { "gen": { "height": 1320246 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e076982e9fa9808fdc9b0c4c115da476fb993499d952bcaf80d5df12a7f89e70" } } ], "extra": [ 1, 106, 213, 153, 31, 231, 66, 53, 89, 182, 216, 93, 27, 222, 168, 10, 178, 144, 164, 168, 56, 205, 179, 47, 147, 252, 162, 158, 156, 199, 70, 48, 143, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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