Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0514924a5f5fb37789b1a6d3bad0f6b728513b806c7f7fe3a0cb9eb0ba3e7dc7

Tx prefix hash: 17524e84e94d4c4a45613882ee33eb25f8dbddcbd254a47ff7df5f44f6cc2c4c
Tx public key: 1cb2beab1b29e3b355431549413420d6a89d132770d29626497a8711c30655f5
Timestamp: 1705439805 Timestamp [UCT]: 2024-01-16 21:16:45 Age [y:d:h:m:s]: 01:298:09:11:40
Block: 936823 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 472075 RingCT/type: yes/0
Extra: 011cb2beab1b29e3b355431549413420d6a89d132770d29626497a8711c30655f50211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5a8198682ec3bdc572e93cb5b7d6be87864dad20dbfe0e42bcf1d1ccb044a261 0.600000000000 1394863 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": 936833, "vin": [ { "gen": { "height": 936823 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5a8198682ec3bdc572e93cb5b7d6be87864dad20dbfe0e42bcf1d1ccb044a261" } } ], "extra": [ 1, 28, 178, 190, 171, 27, 41, 227, 179, 85, 67, 21, 73, 65, 52, 32, 214, 168, 157, 19, 39, 112, 210, 150, 38, 73, 122, 135, 17, 195, 6, 85, 245, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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