Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5f22ffd4ec68b41f178ee7355e02e35ef73dd2d8d5fbc4fa572c3d34aa67c003

Tx prefix hash: 4237a5d6e9bd04ed2c39e69a1645db7dc89d6a7877aa2de5292dc8bc823fd569
Tx public key: 3f73b770e5d86ed19f827ec1147ece8a29882c8ccb031bc4524e302262dd57b1
Timestamp: 1731045541 Timestamp [UCT]: 2024-11-08 05:59:01 Age [y:d:h:m:s]: 00:201:13:53:10
Block: 1149044 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 143938 RingCT/type: yes/0
Extra: 013f73b770e5d86ed19f827ec1147ece8a29882c8ccb031bc4524e302262dd57b10211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5a76a9c0e4ab8bc8176af6ab4d6a498150a73eb49053c76e473edc0c3960ffe3 0.600000000000 1634029 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": 1149054, "vin": [ { "gen": { "height": 1149044 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5a76a9c0e4ab8bc8176af6ab4d6a498150a73eb49053c76e473edc0c3960ffe3" } } ], "extra": [ 1, 63, 115, 183, 112, 229, 216, 110, 209, 159, 130, 126, 193, 20, 126, 206, 138, 41, 136, 44, 140, 203, 3, 27, 196, 82, 78, 48, 34, 98, 221, 87, 177, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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