Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b2ded0652312de66980d0365e10eed98304f66880423dc620f4a427adede8749

Tx prefix hash: feca1ad54d8c9cc2853bc41b1161be9d6fef822c0119779854585cbd416d0d00
Tx public key: 10e871445d5dfe0cda273f8e5e511b90f6a622d4f09ddb1b450fe086366ec4d7
Timestamp: 1725838868 Timestamp [UCT]: 2024-09-08 23:41:08 Age [y:d:h:m:s]: 00:044:16:35:17
Block: 1105974 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 31973 RingCT/type: yes/0
Extra: 0110e871445d5dfe0cda273f8e5e511b90f6a622d4f09ddb1b450fe086366ec4d7021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 734147d1fa25a8db0f0847835b8ac38ae4737b320b0d3c572ae5e8c179ed1c9b 0.600000000000 1583497 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": 1105984, "vin": [ { "gen": { "height": 1105974 } } ], "vout": [ { "amount": 600000000, "target": { "key": "734147d1fa25a8db0f0847835b8ac38ae4737b320b0d3c572ae5e8c179ed1c9b" } } ], "extra": [ 1, 16, 232, 113, 68, 93, 93, 254, 12, 218, 39, 63, 142, 94, 81, 27, 144, 246, 166, 34, 212, 240, 157, 219, 27, 69, 15, 224, 134, 54, 110, 196, 215, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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