Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e2c27432cbeaa89e84d55b7d32cdaedcfc98226fd746d4e62b66b54c412468a1

Tx prefix hash: 175d11805dc03a5705a422046aafee3014c7a6e71d17670124f7125522da01c4
Tx public key: 15f1becf7b3bfed304dfdb21d40dbaad44ba03c2bdc717a2edf659c3bcffc055
Timestamp: 1697121884 Timestamp [UCT]: 2023-10-12 14:44:44 Age [y:d:h:m:s]: 01:138:18:40:35
Block: 868103 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 360171 RingCT/type: yes/0
Extra: 0115f1becf7b3bfed304dfdb21d40dbaad44ba03c2bdc717a2edf659c3bcffc055021100000001e08532b6000000000000000000

1 output(s) for total of 0.815857714000 dcy

stealth address amount amount idx
00: 9eec0f2e8aa89dc3e97d99bb44c79ec91d8bf371247d1c9295b71ed1040bd438 0.815857714000 1322868 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": 868113, "vin": [ { "gen": { "height": 868103 } } ], "vout": [ { "amount": 815857714, "target": { "key": "9eec0f2e8aa89dc3e97d99bb44c79ec91d8bf371247d1c9295b71ed1040bd438" } } ], "extra": [ 1, 21, 241, 190, 207, 123, 59, 254, 211, 4, 223, 219, 33, 212, 13, 186, 173, 68, 186, 3, 194, 189, 199, 23, 162, 237, 246, 89, 195, 188, 255, 192, 85, 2, 17, 0, 0, 0, 1, 224, 133, 50, 182, 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