Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7cde014b0a22bbd2d19417f6644bbd35b74e6fc3e9c25aba46119be1372a2a81

Tx prefix hash: 79de81e3e1e30157adb6bea5b30a98e0ba57368a34a29a340dfd97f90981b14d
Tx public key: 2413c2dd4a6cd66293c066c8c538f5f5e844310963ae13cadca8c9ec2e6a9710
Timestamp: 1708736734 Timestamp [UCT]: 2024-02-24 01:05:34 Age [y:d:h:m:s]: 01:064:13:42:51
Block: 964179 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 307194 RingCT/type: yes/0
Extra: 012413c2dd4a6cd66293c066c8c538f5f5e844310963ae13cadca8c9ec2e6a97100211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 68d3e4403b926b13a0f712cf530e80d3c8589ccfcfe9e3104211c381854d0c27 0.600000000000 1423906 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": 964189, "vin": [ { "gen": { "height": 964179 } } ], "vout": [ { "amount": 600000000, "target": { "key": "68d3e4403b926b13a0f712cf530e80d3c8589ccfcfe9e3104211c381854d0c27" } } ], "extra": [ 1, 36, 19, 194, 221, 74, 108, 214, 98, 147, 192, 102, 200, 197, 56, 245, 245, 232, 68, 49, 9, 99, 174, 19, 202, 220, 168, 201, 236, 46, 106, 151, 16, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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