Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b3154a503adbe285ee977c9a928a3fa7f51d63a9f7ee5d7390fc1958095293c8

Tx prefix hash: 9c32a0c6db5cd7a54d205f2e18f7af957bbacb189d0c736036401b199757ba7a
Tx public key: d9806428356b86d1a6e35377bcf9c4dc62b07568ff7c6cbc46b1d9a8937987b1
Timestamp: 1745270553 Timestamp [UCT]: 2025-04-21 21:22:33 Age [y:d:h:m:s]: 00:022:20:04:52
Block: 1266550 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 16342 RingCT/type: yes/0
Extra: 01d9806428356b86d1a6e35377bcf9c4dc62b07568ff7c6cbc46b1d9a8937987b1021100000003f8f51409000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 167135a3c4398bbb617fc56d6ee052717fa73a5604ba3a2683a35a44f4c600c8 0.600000000000 1753771 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": 1266560, "vin": [ { "gen": { "height": 1266550 } } ], "vout": [ { "amount": 600000000, "target": { "key": "167135a3c4398bbb617fc56d6ee052717fa73a5604ba3a2683a35a44f4c600c8" } } ], "extra": [ 1, 217, 128, 100, 40, 53, 107, 134, 209, 166, 227, 83, 119, 188, 249, 196, 220, 98, 176, 117, 104, 255, 124, 108, 188, 70, 177, 217, 168, 147, 121, 135, 177, 2, 17, 0, 0, 0, 3, 248, 245, 20, 9, 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