Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c8b3943841c1b170b6fe9e968520c9540339e3d9a6010c135e0e3133aa6169e8

Tx prefix hash: 8f794e8504a94ab9b143fb1755cfb31940cafc9857f648686f5ce8bb2c34d7f4
Tx public key: 41007bba9183fd9e58e131356493fc6fd5a3dafaa15cebcc95d6ebf17c65e298
Timestamp: 1697443621 Timestamp [UCT]: 2023-10-16 08:07:01 Age [y:d:h:m:s]: 01:184:03:36:04
Block: 870750 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 392647 RingCT/type: yes/0
Extra: 0141007bba9183fd9e58e131356493fc6fd5a3dafaa15cebcc95d6ebf17c65e298021100000001faf35c9c000000000000000000

1 output(s) for total of 0.799546655000 dcy

stealth address amount amount idx
00: a0b80c8e18308f743d69ddf09d21cddcf8155ce1f90f3a1d5eedc683f3329477 0.799546655000 1325637 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": 870760, "vin": [ { "gen": { "height": 870750 } } ], "vout": [ { "amount": 799546655, "target": { "key": "a0b80c8e18308f743d69ddf09d21cddcf8155ce1f90f3a1d5eedc683f3329477" } } ], "extra": [ 1, 65, 0, 123, 186, 145, 131, 253, 158, 88, 225, 49, 53, 100, 147, 252, 111, 213, 163, 218, 250, 161, 92, 235, 204, 149, 214, 235, 241, 124, 101, 226, 152, 2, 17, 0, 0, 0, 1, 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