Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dfe3d058225f0ea09bcd680a45a1de61072d7c056ec92c36ec2bd78353992e0f

Tx prefix hash: f5e46faf2fafde72e8411f8b3cf5ce49f181c0424a4ac7b441d79185d8242fab
Tx public key: 22f840342c143e47039972d578cbeafe4f6a2071af853a703d42cfe8bb887b4a
Timestamp: 1677767073 Timestamp [UCT]: 2023-03-02 14:24:33 Age [y:d:h:m:s]: 02:038:05:16:09
Block: 708308 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 548880 RingCT/type: yes/0
Extra: 0122f840342c143e47039972d578cbeafe4f6a2071af853a703d42cfe8bb887b4a0211000000037e406890000000000000000000

1 output(s) for total of 2.761095731000 dcy

stealth address amount amount idx
00: 970b4c165452bc2b995c6192b27e963aaf2dbc778a6907f6e9f8e74a699c5233 2.761095731000 1152165 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": 708318, "vin": [ { "gen": { "height": 708308 } } ], "vout": [ { "amount": 2761095731, "target": { "key": "970b4c165452bc2b995c6192b27e963aaf2dbc778a6907f6e9f8e74a699c5233" } } ], "extra": [ 1, 34, 248, 64, 52, 44, 20, 62, 71, 3, 153, 114, 213, 120, 203, 234, 254, 79, 106, 32, 113, 175, 133, 58, 112, 61, 66, 207, 232, 187, 136, 123, 74, 2, 17, 0, 0, 0, 3, 126, 64, 104, 144, 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