Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7e5304e7b0b4f85a89631f270646ea75b392f0d21b488fef1c8fe78b4fe953b4

Tx prefix hash: ffa2ba7ed475cd4fd144ec4fec97978ba7cf05e81c64528a0218f839de82db2c
Tx public key: 33b80101c1bbe4e13ddd3d0ad8596f2be5232fa79307d878e2982ca48bd36467
Timestamp: 1724498347 Timestamp [UCT]: 2024-08-24 11:19:07 Age [y:d:h:m:s]: 00:226:18:18:15
Block: 1094859 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 161902 RingCT/type: yes/0
Extra: 0133b80101c1bbe4e13ddd3d0ad8596f2be5232fa79307d878e2982ca48bd3646702110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bf4eade3c0d0b3e5e03e84d8ff475f31f72c12e63cc549c9f8366f3e43a3c131 0.600000000000 1569980 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": 1094869, "vin": [ { "gen": { "height": 1094859 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bf4eade3c0d0b3e5e03e84d8ff475f31f72c12e63cc549c9f8366f3e43a3c131" } } ], "extra": [ 1, 51, 184, 1, 1, 193, 187, 228, 225, 61, 221, 61, 10, 216, 89, 111, 43, 229, 35, 47, 167, 147, 7, 216, 120, 226, 152, 44, 164, 139, 211, 100, 103, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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