Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 376eab209863580f8aabc5061b63fbb50ff5c2c039dfe8c31474725a60ebdc1e

Tx prefix hash: e9a5b796ff56dd24f2e42ed0a282307b88a60a94b24a484fcde1dc488f299d39
Tx public key: 0dd524011d4a5ad11dbcb7eb44d4dfe28a0b5fe8c864f3a83026cbd4f514b2b9
Timestamp: 1681694147 Timestamp [UCT]: 2023-04-17 01:15:47 Age [y:d:h:m:s]: 01:315:10:41:14
Block: 740220 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 486696 RingCT/type: yes/0
Extra: 010dd524011d4a5ad11dbcb7eb44d4dfe28a0b5fe8c864f3a83026cbd4f514b2b9021100000003faf35c9c000000000000000000

1 output(s) for total of 2.164432655000 dcy

stealth address amount amount idx
00: 0c3d15869fdb09b0f5de069e0c7673d0c71560e54cccb7144cfc022b3cc4f0b9 2.164432655000 1187105 of 0

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": 740230, "vin": [ { "gen": { "height": 740220 } } ], "vout": [ { "amount": 2164432655, "target": { "key": "0c3d15869fdb09b0f5de069e0c7673d0c71560e54cccb7144cfc022b3cc4f0b9" } } ], "extra": [ 1, 13, 213, 36, 1, 29, 74, 90, 209, 29, 188, 183, 235, 68, 212, 223, 226, 138, 11, 95, 232, 200, 100, 243, 168, 48, 38, 203, 212, 245, 20, 178, 185, 2, 17, 0, 0, 0, 3, 250, 243, 92, 156, 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