Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c32a8b0414c6f7faa50f75cc4ae8d602088f2cd3f6318affe82ba4d060c7c75

Tx prefix hash: f468dcdaf26968574732214aaeb50a322f52271fd563fe6e5e13ad18cf05b18f
Tx public key: e672c800c1865573955a38e0718be73553224dfb70697f8f31e6960a4cc7d1ea
Timestamp: 1736374493 Timestamp [UCT]: 2025-01-08 22:14:53 Age [y:d:h:m:s]: 00:163:15:19:56
Block: 1193170 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 116619 RingCT/type: yes/0
Extra: 01e672c800c1865573955a38e0718be73553224dfb70697f8f31e6960a4cc7d1ea021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bc7fa779225c66be795cf7b5ff4de2aa11e3bcf09021fb0ef0c603c8926e2e8c 0.600000000000 1679729 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": 1193180, "vin": [ { "gen": { "height": 1193170 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bc7fa779225c66be795cf7b5ff4de2aa11e3bcf09021fb0ef0c603c8926e2e8c" } } ], "extra": [ 1, 230, 114, 200, 0, 193, 134, 85, 115, 149, 90, 56, 224, 113, 139, 231, 53, 83, 34, 77, 251, 112, 105, 127, 143, 49, 230, 150, 10, 76, 199, 209, 234, 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