Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b0a41c66009e80c21bb5baec821d0a969e61fe0b6557e87e816f37301289675b

Tx prefix hash: fefe2052a9dfe5701602116c2ba3b9be3249f96c3bcefd1f4dee6a8afe664e3b
Tx public key: bb8357ec51b82f527f13494a46fa6b42dc6d55e0788024e341bc5189a2126d6d
Timestamp: 1719820260 Timestamp [UCT]: 2024-07-01 07:51:00 Age [y:d:h:m:s]: 01:215:02:08:46
Block: 1056064 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 412188 RingCT/type: yes/0
Extra: 01bb8357ec51b82f527f13494a46fa6b42dc6d55e0788024e341bc5189a2126d6d02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e827f1ea9508901ce536475f35c7fc870e546f8f2d5048892c711fcdf5367e8b 0.600000000000 1526475 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": 1056074, "vin": [ { "gen": { "height": 1056064 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e827f1ea9508901ce536475f35c7fc870e546f8f2d5048892c711fcdf5367e8b" } } ], "extra": [ 1, 187, 131, 87, 236, 81, 184, 47, 82, 127, 19, 73, 74, 70, 250, 107, 66, 220, 109, 85, 224, 120, 128, 36, 227, 65, 188, 81, 137, 162, 18, 109, 109, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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