Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b177b97263c3797be52f1cc724f03e3cab5459eed48a5fd10754f1a2bf58da2f

Tx prefix hash: 5b6b8e58d79c814d5c976e7b2cc3d868d1bf1f8c19af2d22bcc30ce9401692c0
Tx public key: 33acaa2d9c3a71707fcfda681f528cde315d844559319f562e639ee396c5ca23
Timestamp: 1745752359 Timestamp [UCT]: 2025-04-27 11:12:39 Age [y:d:h:m:s]: 00:239:14:48:38
Block: 1270547 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 169014 RingCT/type: yes/0
Extra: 0133acaa2d9c3a71707fcfda681f528cde315d844559319f562e639ee396c5ca230211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 95990d97207c69e3e434ca3c7935a2cef88afda10c58a015ee11de217596f392 0.600000000000 1757790 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": 1270557, "vin": [ { "gen": { "height": 1270547 } } ], "vout": [ { "amount": 600000000, "target": { "key": "95990d97207c69e3e434ca3c7935a2cef88afda10c58a015ee11de217596f392" } } ], "extra": [ 1, 51, 172, 170, 45, 156, 58, 113, 112, 127, 207, 218, 104, 31, 82, 140, 222, 49, 93, 132, 69, 89, 49, 159, 86, 46, 99, 158, 227, 150, 197, 202, 35, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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