Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 541ae5fa32e3750a25ffbf72eaca5969e8728431fd9e7d645f9e25e7e9f8263b

Tx prefix hash: a72a5bd92e1cfa95fdfef651b84a0b9ff06a2648786d88452ec7f57880f2afb3
Tx public key: 1babe63ca2d469695cdb0e74835c1b7055e1ae8d428d880faba96b37f5712915
Timestamp: 1726148324 Timestamp [UCT]: 2024-09-12 13:38:44 Age [y:d:h:m:s]: 00:206:08:06:16
Block: 1108522 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 147294 RingCT/type: yes/0
Extra: 011babe63ca2d469695cdb0e74835c1b7055e1ae8d428d880faba96b37f5712915021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6559a949bddc938494e5dd8a044b91cccb9bc52d6eae1326302f2a57a2a276e3 0.600000000000 1586447 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": 1108532, "vin": [ { "gen": { "height": 1108522 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6559a949bddc938494e5dd8a044b91cccb9bc52d6eae1326302f2a57a2a276e3" } } ], "extra": [ 1, 27, 171, 230, 60, 162, 212, 105, 105, 92, 219, 14, 116, 131, 92, 27, 112, 85, 225, 174, 141, 66, 141, 136, 15, 171, 169, 107, 55, 245, 113, 41, 21, 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