Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e398aafe482bba21c6a4afbcfcee60b24e8839e84cfa90ab09149aa69c254ee1

Tx prefix hash: 49323bb12a73c52c1f469b437917752f8f46b6f74bc16ebe7e80d9fac27878ee
Tx public key: 4d3093cbb40a7a6a7bc2e79ae3151e2f2d3cbb39b4d47ce62283142909703e74
Timestamp: 1729754111 Timestamp [UCT]: 2024-10-24 07:15:11 Age [y:d:h:m:s]: 00:161:12:36:41
Block: 1138394 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115224 RingCT/type: yes/0
Extra: 014d3093cbb40a7a6a7bc2e79ae3151e2f2d3cbb39b4d47ce62283142909703e74021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 74865ed1a525651f006f992ba6b03ce4e3774cf08396cd50fd0bf92b3881c97b 0.600000000000 1622053 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": 1138404, "vin": [ { "gen": { "height": 1138394 } } ], "vout": [ { "amount": 600000000, "target": { "key": "74865ed1a525651f006f992ba6b03ce4e3774cf08396cd50fd0bf92b3881c97b" } } ], "extra": [ 1, 77, 48, 147, 203, 180, 10, 122, 106, 123, 194, 231, 154, 227, 21, 30, 47, 45, 60, 187, 57, 180, 212, 124, 230, 34, 131, 20, 41, 9, 112, 62, 116, 2, 17, 0, 0, 0, 3, 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