Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3a2b37941ae64fb9e6cb5fb2d29b446662b5113b70bd1d29a4084863cbcdbd95

Tx prefix hash: 74af860a61d564f3b767551cfded73089c7afb465c0f96bfa0eab45bbb1d0fac
Tx public key: 9138dff9e64d30e53fadd73245d1b8000123546cbd8b1ed516437a9ddc8c5fb6
Timestamp: 1734511376 Timestamp [UCT]: 2024-12-18 08:42:56 Age [y:d:h:m:s]: 00:103:03:43:52
Block: 1177771 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 73493 RingCT/type: yes/0
Extra: 019138dff9e64d30e53fadd73245d1b8000123546cbd8b1ed516437a9ddc8c5fb6021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 217bc9ef166ca818eae9d25cdb4e9bb7ed3b55366af16da05f432c74bfba64ba 0.600000000000 1664148 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": 1177781, "vin": [ { "gen": { "height": 1177771 } } ], "vout": [ { "amount": 600000000, "target": { "key": "217bc9ef166ca818eae9d25cdb4e9bb7ed3b55366af16da05f432c74bfba64ba" } } ], "extra": [ 1, 145, 56, 223, 249, 230, 77, 48, 229, 63, 173, 215, 50, 69, 209, 184, 0, 1, 35, 84, 108, 189, 139, 30, 213, 22, 67, 122, 157, 220, 140, 95, 182, 2, 17, 0, 0, 0, 1, 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