Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 210da63e64f749bed8831257b461a4d84a660a8ff5cdb21a725e29a626481e87

Tx prefix hash: 670404db6d9a139376b1fd66ce690e69fbb8162afedaad326008f3183fad8e29
Tx public key: 3b2719ac63bbcdbb274201a02cf8461be93b4df8c8aec64a4ce6f37511a2f4ab
Timestamp: 1574935711 Timestamp [UCT]: 2019-11-28 10:08:31 Age [y:d:h:m:s]: 05:188:18:13:00
Block: 18944 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1277861 RingCT/type: yes/0
Extra: 013b2719ac63bbcdbb274201a02cf8461be93b4df8c8aec64a4ce6f37511a2f4ab021100000001ad433a0b000000000000000000

1 output(s) for total of 531.167558592000 dcy

stealth address amount amount idx
00: 364f6449fc629e9b9088181f4270158fe07d9553d29cd570d00a7a051cddfbf7 531.167558592000 29643 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": 18954, "vin": [ { "gen": { "height": 18944 } } ], "vout": [ { "amount": 531167558592, "target": { "key": "364f6449fc629e9b9088181f4270158fe07d9553d29cd570d00a7a051cddfbf7" } } ], "extra": [ 1, 59, 39, 25, 172, 99, 187, 205, 187, 39, 66, 1, 160, 44, 248, 70, 27, 233, 59, 77, 248, 200, 174, 198, 74, 76, 230, 243, 117, 17, 162, 244, 171, 2, 17, 0, 0, 0, 1, 173, 67, 58, 11, 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