Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 79dbf26a2b4f8d032f38c1c3b59a8d4f95c74d7e80cd0c86e2d0aa57df589a6d

Tx prefix hash: 4521e1052f2036fd7e9bdf6c788ff54583ed1765ab4e994466794aef503170ca
Tx public key: 11fa3945a677edea7f19038241047e5d86cf4108de7d077f6b8b74ae9e5e5ee7
Timestamp: 1698353899 Timestamp [UCT]: 2023-10-26 20:58:19 Age [y:d:h:m:s]: 01:088:12:01:51
Block: 878313 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 324428 RingCT/type: yes/0
Extra: 0111fa3945a677edea7f19038241047e5d86cf4108de7d077f6b8b74ae9e5e5ee70211000000034b8f5122000000000000000000

1 output(s) for total of 0.754717536000 dcy

stealth address amount amount idx
00: cce64e270f7f56c5812a9f8771b49d0247e35ed1af3b9641b028f25a52c51666 0.754717536000 1333747 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": 878323, "vin": [ { "gen": { "height": 878313 } } ], "vout": [ { "amount": 754717536, "target": { "key": "cce64e270f7f56c5812a9f8771b49d0247e35ed1af3b9641b028f25a52c51666" } } ], "extra": [ 1, 17, 250, 57, 69, 166, 119, 237, 234, 127, 25, 3, 130, 65, 4, 126, 93, 134, 207, 65, 8, 222, 125, 7, 127, 107, 139, 116, 174, 158, 94, 94, 231, 2, 17, 0, 0, 0, 3, 75, 143, 81, 34, 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