Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 11a6807e88025bc3d06ac6d0125f776494cd696e445ddcbedf30b8e350fee637

Tx prefix hash: 8409d675ba7a2f79d91ad40b5d75b810fc100e77b6d2ea93c63b64c4d95e1d28
Tx public key: fcd2c6c62b1913c9ae52605dc97b0179be5ec286e70e5efb42ff41717b7e50ec
Timestamp: 1747501604 Timestamp [UCT]: 2025-05-17 17:06:44 Age [y:d:h:m:s]: 00:186:09:08:40
Block: 1285017 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 130920 RingCT/type: yes/0
Extra: 01fcd2c6c62b1913c9ae52605dc97b0179be5ec286e70e5efb42ff41717b7e50ec0211000000059f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 41f6538caffa2c18e30d8338a24054b3a10cc353d85133c3cc2ce773131b673f 0.600000000000 1772480 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": 1285027, "vin": [ { "gen": { "height": 1285017 } } ], "vout": [ { "amount": 600000000, "target": { "key": "41f6538caffa2c18e30d8338a24054b3a10cc353d85133c3cc2ce773131b673f" } } ], "extra": [ 1, 252, 210, 198, 198, 43, 25, 19, 201, 174, 82, 96, 93, 201, 123, 1, 121, 190, 94, 194, 134, 231, 14, 94, 251, 66, 255, 65, 113, 123, 126, 80, 236, 2, 17, 0, 0, 0, 5, 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