Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 75e7572ae3c3f662b25bd595c5a055690e4eb2eddb0c7a19af1c702ae3b42fcc

Tx prefix hash: a6cff6072240649086b74846d4cad4ea4a2302c0bda954f3ae9077924078cae9
Tx public key: 0364212f6b894d4fb14cc2d59c802ec47ed46ca9e5ef8f40225053538e2c8502
Timestamp: 1746361795 Timestamp [UCT]: 2025-05-04 12:29:55 Age [y:d:h:m:s]: 00:194:12:02:56
Block: 1275580 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 136725 RingCT/type: yes/0
Extra: 010364212f6b894d4fb14cc2d59c802ec47ed46ca9e5ef8f40225053538e2c85020211000000029f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dca1b393469b7f7c45b2f557ac0f169793a6c66033a7da569d46c926d54d8193 0.600000000000 1762895 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": 1275590, "vin": [ { "gen": { "height": 1275580 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dca1b393469b7f7c45b2f557ac0f169793a6c66033a7da569d46c926d54d8193" } } ], "extra": [ 1, 3, 100, 33, 47, 107, 137, 77, 79, 177, 76, 194, 213, 156, 128, 46, 196, 126, 212, 108, 169, 229, 239, 143, 64, 34, 80, 83, 83, 142, 44, 133, 2, 2, 17, 0, 0, 0, 2, 159, 159, 230, 140, 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