Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d78fee8ae78603046aff81f1f33c725ea881922485ec4b317a194597386816bf

Tx prefix hash: 3c416f3c7b1a0fbd4ad9c40418ba121e3d22d0159a2f2f271df50e2a9f215d18
Tx public key: ff71a59fa1df69ca8ad5ad27989459652a538755afdca37b8a2a58dc5bc23ffb
Timestamp: 1705173300 Timestamp [UCT]: 2024-01-13 19:15:00 Age [y:d:h:m:s]: 01:079:21:04:10
Block: 934622 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 318187 RingCT/type: yes/0
Extra: 01ff71a59fa1df69ca8ad5ad27989459652a538755afdca37b8a2a58dc5bc23ffb0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3b7869a7cda1e481dc08f4ef5a4e67326899cd9d2b1e2518da1648a0b84cc5c8 0.600000000000 1392636 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": 934632, "vin": [ { "gen": { "height": 934622 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3b7869a7cda1e481dc08f4ef5a4e67326899cd9d2b1e2518da1648a0b84cc5c8" } } ], "extra": [ 1, 255, 113, 165, 159, 161, 223, 105, 202, 138, 213, 173, 39, 152, 148, 89, 101, 42, 83, 135, 85, 175, 220, 163, 123, 138, 42, 88, 220, 91, 194, 63, 251, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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