Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7b01901442a1f835e00ead11f4a2941e3e8bf21a1be7134be86a740e3a01913f

Tx prefix hash: 8698f20eead0c5d704c3bf6f4a334aa0cf50d51d2a0cc4b1b20cd93663cd5ef0
Tx public key: a5fa7b99a88376b37894842fb536f80cf6dfaf95fa160ccd19ab7668f192921d
Timestamp: 1734440624 Timestamp [UCT]: 2024-12-17 13:03:44 Age [y:d:h:m:s]: 00:104:08:57:02
Block: 1177189 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 74360 RingCT/type: yes/0
Extra: 01a5fa7b99a88376b37894842fb536f80cf6dfaf95fa160ccd19ab7668f192921d0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c8485b417be2ce004414463a5e6b68d9624da3bea47b5d5875210b0d6b0d4a98 0.600000000000 1663554 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": 1177199, "vin": [ { "gen": { "height": 1177189 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c8485b417be2ce004414463a5e6b68d9624da3bea47b5d5875210b0d6b0d4a98" } } ], "extra": [ 1, 165, 250, 123, 153, 168, 131, 118, 179, 120, 148, 132, 47, 181, 54, 248, 12, 246, 223, 175, 149, 250, 22, 12, 205, 25, 171, 118, 104, 241, 146, 146, 29, 2, 17, 0, 0, 0, 4, 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