Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b51158fa4b3346ec071d3d1f8be6c7349d3b9ecf2fd4b3efae4021e4e592db44

Tx prefix hash: befc0293a79a75ac64075b59453866c54bebff88282cb451abce20755738c04e
Tx public key: cfed1242f50c24d7a2b153e40985dc274436e18673c8ba6a4e247d621cebcdd2
Timestamp: 1697035977 Timestamp [UCT]: 2023-10-11 14:52:57 Age [y:d:h:m:s]: 01:093:14:15:52
Block: 867382 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 328135 RingCT/type: yes/0
Extra: 01cfed1242f50c24d7a2b153e40985dc274436e18673c8ba6a4e247d621cebcdd202110000000efaf35c9c000000000000000000

1 output(s) for total of 0.820357962000 dcy

stealth address amount amount idx
00: 08e315681c83b22d2cf48da87a531252c1d2b09422b05a2c0abba1d919698ce8 0.820357962000 1322060 of 0

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": 867392, "vin": [ { "gen": { "height": 867382 } } ], "vout": [ { "amount": 820357962, "target": { "key": "08e315681c83b22d2cf48da87a531252c1d2b09422b05a2c0abba1d919698ce8" } } ], "extra": [ 1, 207, 237, 18, 66, 245, 12, 36, 215, 162, 177, 83, 228, 9, 133, 220, 39, 68, 54, 225, 134, 115, 200, 186, 106, 78, 36, 125, 98, 28, 235, 205, 210, 2, 17, 0, 0, 0, 14, 250, 243, 92, 156, 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