Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bfaa4e8c22a72398a31a2adaef9c767c33dcd3672a7da060ee70e75643d83620

Tx prefix hash: 9dff8c6259216396bc9860142c5d626be39e7221b10d4b8f70d858575670461b
Tx public key: 174fe28b2d6a60841b4f6170024da6efa7f7ce609b4ab47b3bb22cb0f2a0d71e
Timestamp: 1737436303 Timestamp [UCT]: 2025-01-21 05:11:43 Age [y:d:h:m:s]: 00:148:21:15:14
Block: 1201911 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106142 RingCT/type: yes/0
Extra: 01174fe28b2d6a60841b4f6170024da6efa7f7ce609b4ab47b3bb22cb0f2a0d71e0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1fcac5257c09534a0b34f60b0c2f8c50b74533d165d9ce10d9089f9290f5c3e7 0.600000000000 1688570 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": 1201921, "vin": [ { "gen": { "height": 1201911 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1fcac5257c09534a0b34f60b0c2f8c50b74533d165d9ce10d9089f9290f5c3e7" } } ], "extra": [ 1, 23, 79, 226, 139, 45, 106, 96, 132, 27, 79, 97, 112, 2, 77, 166, 239, 167, 247, 206, 96, 155, 74, 180, 123, 59, 178, 44, 176, 242, 160, 215, 30, 2, 17, 0, 0, 0, 2, 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