Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f549146750b1fce19e964b786467df29dd1a402223dc6ca00fa9a4e4b5996d2d

Tx prefix hash: ea2554dc186196481b68db6116cbf2c503d5332d67a467a6a4e012cfc081eb9f
Tx public key: a07908257da5fcbc3f550963d8e9da4d989cb06664f4ac4ab79a8c1f11415428
Timestamp: 1738190672 Timestamp [UCT]: 2025-01-29 22:44:32 Age [y:d:h:m:s]: 00:294:23:07:40
Block: 1207946 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 208568 RingCT/type: yes/0
Extra: 01a07908257da5fcbc3f550963d8e9da4d989cb06664f4ac4ab79a8c1f11415428021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ef8a06a894b33311f008a3caa88a258f39c1543df68c2a1383db9e4b418b328f 0.600000000000 1694673 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": 1207956, "vin": [ { "gen": { "height": 1207946 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ef8a06a894b33311f008a3caa88a258f39c1543df68c2a1383db9e4b418b328f" } } ], "extra": [ 1, 160, 121, 8, 37, 125, 165, 252, 188, 63, 85, 9, 99, 216, 233, 218, 77, 152, 156, 176, 102, 100, 244, 172, 74, 183, 154, 140, 31, 17, 65, 84, 40, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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