Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 074ff40ac54a9858c6fac99c7db16a140bea1aefc044c129e924dbcb39ac314d

Tx prefix hash: e62a9e45e61668cda343c9614ffe86f4911e5d3b78ee03b304628a040c626446
Tx public key: 53392690943201682c8b759f5d9ffa3e3f169491a134bfd6c7ae3f3858b9b1cb
Timestamp: 1727370758 Timestamp [UCT]: 2024-09-26 17:12:38 Age [y:d:h:m:s]: 00:188:02:03:51
Block: 1118663 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 134228 RingCT/type: yes/0
Extra: 0153392690943201682c8b759f5d9ffa3e3f169491a134bfd6c7ae3f3858b9b1cb021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bbe18a7107064c436fe4e8f265b87512da91263a1efb8f83a2ef2c4ed588460e 0.600000000000 1599934 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": 1118673, "vin": [ { "gen": { "height": 1118663 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bbe18a7107064c436fe4e8f265b87512da91263a1efb8f83a2ef2c4ed588460e" } } ], "extra": [ 1, 83, 57, 38, 144, 148, 50, 1, 104, 44, 139, 117, 159, 93, 159, 250, 62, 63, 22, 148, 145, 161, 52, 191, 214, 199, 174, 63, 56, 88, 185, 177, 203, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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