Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 153876a3426b3d1b74c5e1c4472cfdde8d3ab7dae853d98b69b9a5e8f687311f

Tx prefix hash: cddb75fb2a442f3a01a58ebf82b966244548ed4a72db360cb3239af5dda83e79
Tx public key: 58c9c525e5f07fb4cfe76a1aff154516a35a4d50a4a4538ad0ba4fe7d8121c00
Timestamp: 1577646083 Timestamp [UCT]: 2019-12-29 19:01:23 Age [y:d:h:m:s]: 05:115:09:31:39
Block: 34494 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1232262 RingCT/type: yes/0
Extra: 0158c9c525e5f07fb4cfe76a1aff154516a35a4d50a4a4538ad0ba4fe7d8121c000211000000054943cd9f000000000000000000

1 output(s) for total of 471.745661259000 dcy

stealth address amount amount idx
00: bf03e658870887e5a78d5a1e03e67ca8cd0fbb699fba51c7a765e6f656e51c51 471.745661259000 58060 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": 34504, "vin": [ { "gen": { "height": 34494 } } ], "vout": [ { "amount": 471745661259, "target": { "key": "bf03e658870887e5a78d5a1e03e67ca8cd0fbb699fba51c7a765e6f656e51c51" } } ], "extra": [ 1, 88, 201, 197, 37, 229, 240, 127, 180, 207, 231, 106, 26, 255, 21, 69, 22, 163, 90, 77, 80, 164, 164, 83, 138, 208, 186, 79, 231, 216, 18, 28, 0, 2, 17, 0, 0, 0, 5, 73, 67, 205, 159, 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