Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 52862d11ca8fc975894243f3fff64737de6c0e3531e22a6dd596c4397e94a85d

Tx prefix hash: cc848b5a8807cfaffb0a8ef1fe6a2c809cfa44312fd142fc50d11749411ebb9c
Tx public key: ca94eba964fb8d709a39cd9ea0c7f150d70e8e27cc74e534cbaf28de6e3d06e5
Timestamp: 1718512025 Timestamp [UCT]: 2024-06-16 04:27:05 Age [y:d:h:m:s]: 00:331:17:00:47
Block: 1045232 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 237059 RingCT/type: yes/0
Extra: 01ca94eba964fb8d709a39cd9ea0c7f150d70e8e27cc74e534cbaf28de6e3d06e50211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6a1c7ba788b8c5393ce09f0c1050ca562db25ae5c09881f7f78ae1b729b82736 0.600000000000 1514749 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": 1045242, "vin": [ { "gen": { "height": 1045232 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6a1c7ba788b8c5393ce09f0c1050ca562db25ae5c09881f7f78ae1b729b82736" } } ], "extra": [ 1, 202, 148, 235, 169, 100, 251, 141, 112, 154, 57, 205, 158, 160, 199, 241, 80, 215, 14, 142, 39, 204, 116, 229, 52, 203, 175, 40, 222, 110, 61, 6, 229, 2, 17, 0, 0, 0, 1, 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