Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 299198aebb4eceb42b47218eb49bc2547c92972c85f185a937718545cc9b3d4f

Tx prefix hash: e1601418a1a90846695c5b980e2d6a0e90910b44ed6555f6a46665d0fac489c8
Tx public key: 61400c5a2860d30758e622d1f32346c86fef9f3c94348eaf21d11d7c34d29cf3
Timestamp: 1711527081 Timestamp [UCT]: 2024-03-27 08:11:21 Age [y:d:h:m:s]: 00:334:12:55:47
Block: 987338 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 239136 RingCT/type: yes/0
Extra: 0161400c5a2860d30758e622d1f32346c86fef9f3c94348eaf21d11d7c34d29cf30211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eebbb58d061dbf2a84a5aefca7731bcaee1d0f54ed2e957cad439df3eaaa0741 0.600000000000 1447579 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": 987348, "vin": [ { "gen": { "height": 987338 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eebbb58d061dbf2a84a5aefca7731bcaee1d0f54ed2e957cad439df3eaaa0741" } } ], "extra": [ 1, 97, 64, 12, 90, 40, 96, 211, 7, 88, 230, 34, 209, 243, 35, 70, 200, 111, 239, 159, 60, 148, 52, 142, 175, 33, 209, 29, 124, 52, 210, 156, 243, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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