Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bff40d7afc8535210b568180fd81a46f29ac3d22c5a7a01309d7bb6532a5f31c

Tx prefix hash: 965affc2cc08232292474833a6ec225a44e3fedd2cffed2468e1d7521f5d3e2a
Tx public key: fc1bc6ba48a6c7a2b7647eb6104ae68c2a83b242119a8c81b52ca54b18d0297f
Timestamp: 1747038718 Timestamp [UCT]: 2025-05-12 08:31:58 Age [y:d:h:m:s]: 00:192:19:17:22
Block: 1281184 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 135500 RingCT/type: yes/0
Extra: 01fc1bc6ba48a6c7a2b7647eb6104ae68c2a83b242119a8c81b52ca54b18d0297f0211000000029f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7fd046c60b3f76bf87dbfa71060309b9a8002baa137441801d062114ccd12396 0.600000000000 1768583 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": 1281194, "vin": [ { "gen": { "height": 1281184 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7fd046c60b3f76bf87dbfa71060309b9a8002baa137441801d062114ccd12396" } } ], "extra": [ 1, 252, 27, 198, 186, 72, 166, 199, 162, 183, 100, 126, 182, 16, 74, 230, 140, 42, 131, 178, 66, 17, 154, 140, 129, 181, 44, 165, 75, 24, 208, 41, 127, 2, 17, 0, 0, 0, 2, 159, 159, 230, 140, 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