Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bcdb8cecf9a0f5608841bca0028f0a03bbdab147a48f82f9a5059016edaa0d13

Tx prefix hash: f69243b076063de6e7a203555ffe41c0d476eb538387790d38e207e9b11c0e1d
Tx public key: 36688327dc2d0e724120fdf1c6cb48452861a59e25f560784dae048b6b9aff88
Timestamp: 1735267945 Timestamp [UCT]: 2024-12-27 02:52:25 Age [y:d:h:m:s]: 00:084:20:29:44
Block: 1183999 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 60437 RingCT/type: yes/0
Extra: 0136688327dc2d0e724120fdf1c6cb48452861a59e25f560784dae048b6b9aff88021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4d7dfbabb03041afe17cada4e0501fd4f635ff3a41c2ba3257d7f425b8e85a7d 0.600000000000 1670450 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": 1184009, "vin": [ { "gen": { "height": 1183999 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4d7dfbabb03041afe17cada4e0501fd4f635ff3a41c2ba3257d7f425b8e85a7d" } } ], "extra": [ 1, 54, 104, 131, 39, 220, 45, 14, 114, 65, 32, 253, 241, 198, 203, 72, 69, 40, 97, 165, 158, 37, 245, 96, 120, 77, 174, 4, 139, 107, 154, 255, 136, 2, 17, 0, 0, 0, 1, 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