Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8296623297d579d5f522f85170fcb20afbd0eb359b1e4ad8fb100390db88fe81

Tx prefix hash: 7cbf23eb2f845680454189b8d0b5315aa49e06aca4a5499223d893b82e3655dd
Tx public key: 5e5b17c536f90a7380f9a59bcaaa62e97869b09bc58c55b2664a403daa930c7d
Timestamp: 1722483266 Timestamp [UCT]: 2024-08-01 03:34:26 Age [y:d:h:m:s]: 00:083:04:39:27
Block: 1078139 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 59564 RingCT/type: yes/0
Extra: 015e5b17c536f90a7380f9a59bcaaa62e97869b09bc58c55b2664a403daa930c7d021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: db9b4c159ff80e458d44b0f2e35e65ec9c13d0a91ff5a746bd5e8552e61d13cb 0.600000000000 1550706 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": 1078149, "vin": [ { "gen": { "height": 1078139 } } ], "vout": [ { "amount": 600000000, "target": { "key": "db9b4c159ff80e458d44b0f2e35e65ec9c13d0a91ff5a746bd5e8552e61d13cb" } } ], "extra": [ 1, 94, 91, 23, 197, 54, 249, 10, 115, 128, 249, 165, 155, 202, 170, 98, 233, 120, 105, 176, 155, 197, 140, 85, 178, 102, 74, 64, 61, 170, 147, 12, 125, 2, 17, 0, 0, 0, 2, 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