Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 646cdd27ef40fa400d1f43633f161d0612096aaa93968bee110787b390997894

Tx prefix hash: 2ac631acd68246c704e85a570f6f0c77a9ebef1699af919eebdb8f5320da3a43
Tx public key: 8b0a00598acfb3f818d9ae0511b3f4268c8408e751f0b87449be750335edc2a9
Timestamp: 1734360169 Timestamp [UCT]: 2024-12-16 14:42:49 Age [y:d:h:m:s]: 00:024:16:55:34
Block: 1176518 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 17647 RingCT/type: yes/0
Extra: 018b0a00598acfb3f818d9ae0511b3f4268c8408e751f0b87449be750335edc2a9021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cdd38325c8622770e408ba3ea537d94d13a01dc89ae082d190fd4d973848232c 0.600000000000 1662859 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": 1176528, "vin": [ { "gen": { "height": 1176518 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cdd38325c8622770e408ba3ea537d94d13a01dc89ae082d190fd4d973848232c" } } ], "extra": [ 1, 139, 10, 0, 89, 138, 207, 179, 248, 24, 217, 174, 5, 17, 179, 244, 38, 140, 132, 8, 231, 81, 240, 184, 116, 73, 190, 117, 3, 53, 237, 194, 169, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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