Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 54a74258ae7d23df355cb4b87d1e3cd1c813c136d732562b60fae1f31e5ee906

Tx prefix hash: 6174c492a80e19f90dea711ed5063eda2c42c05efa7df4998efb16b2fceb98c5
Tx public key: 7bf1aacb48749b5c0ee93214d184ef0e546c12b0ba008a43443c7179253932d7
Timestamp: 1712228526 Timestamp [UCT]: 2024-04-04 11:02:06 Age [y:d:h:m:s]: 00:332:23:11:53
Block: 993103 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 238061 RingCT/type: yes/0
Extra: 017bf1aacb48749b5c0ee93214d184ef0e546c12b0ba008a43443c7179253932d702110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fde0edaa7284526c3f2bd4a1d8c690538a5d2db1a14e596c0db33affe45f1d33 0.600000000000 1453485 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": 993113, "vin": [ { "gen": { "height": 993103 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fde0edaa7284526c3f2bd4a1d8c690538a5d2db1a14e596c0db33affe45f1d33" } } ], "extra": [ 1, 123, 241, 170, 203, 72, 116, 155, 92, 14, 233, 50, 20, 209, 132, 239, 14, 84, 108, 18, 176, 186, 0, 138, 67, 68, 60, 113, 121, 37, 57, 50, 215, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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