Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9a695f7bb05b62a2dbd45068ef4255dff0a6db344480cc706333b6e7f5d390b7

Tx prefix hash: 1381c7c1dc65ece85e28a555dc32a1bd7bb565e6f9b1e2c16b6bc24faf491a25
Tx public key: 57a47a2cdef4385e536e2e9befd42309e4d4ddaa19e47be844a209e2437748b9
Timestamp: 1729240871 Timestamp [UCT]: 2024-10-18 08:41:11 Age [y:d:h:m:s]: 00:036:23:00:46
Block: 1134173 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 26373 RingCT/type: yes/0
Extra: 0157a47a2cdef4385e536e2e9befd42309e4d4ddaa19e47be844a209e2437748b90211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 313522ae1770c7add27fac521a491ca77a03e057533e861ef6c5cc01f4714955 0.600000000000 1617434 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": 1134183, "vin": [ { "gen": { "height": 1134173 } } ], "vout": [ { "amount": 600000000, "target": { "key": "313522ae1770c7add27fac521a491ca77a03e057533e861ef6c5cc01f4714955" } } ], "extra": [ 1, 87, 164, 122, 44, 222, 244, 56, 94, 83, 110, 46, 155, 239, 212, 35, 9, 228, 212, 221, 170, 25, 228, 123, 232, 68, 162, 9, 226, 67, 119, 72, 185, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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