Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ddccb6b6363e28cd41247dc5f33a7051593d0a2e5c8680b3a5c25ddad250388e

Tx prefix hash: 49e23e416c9f7309d33da32a045008af28c96b9119ab62dc09a02209fc0d90ee
Tx public key: c4691b3b089733c79a8af28858ff9c22a4d2d29995d754377e06e28d30c106a9
Timestamp: 1708923935 Timestamp [UCT]: 2024-02-26 05:05:35 Age [y:d:h:m:s]: 01:078:14:43:33
Block: 965736 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 317227 RingCT/type: yes/0
Extra: 01c4691b3b089733c79a8af28858ff9c22a4d2d29995d754377e06e28d30c106a9021100000001679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c00ea10e8f159ff5bb1a853e3844ea14a881042f523060f87c81e2bf8ec40ead 0.600000000000 1425491 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": 965746, "vin": [ { "gen": { "height": 965736 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c00ea10e8f159ff5bb1a853e3844ea14a881042f523060f87c81e2bf8ec40ead" } } ], "extra": [ 1, 196, 105, 27, 59, 8, 151, 51, 199, 154, 138, 242, 136, 88, 255, 156, 34, 164, 210, 210, 153, 149, 215, 84, 55, 126, 6, 226, 141, 48, 193, 6, 169, 2, 17, 0, 0, 0, 1, 103, 154, 138, 129, 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