Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6d85b3bc41703bb4cdc72e3005a9a6d7338c305d484ddcc24f38b5c6fd8fda80

Tx prefix hash: 2a030c5673027014df1c6d1c4c3996658a5d2b9a47644e0046b52584fb78d066
Tx public key: 3653c64fd50d092ad81156995938f1d8bc26897b36a841b883e4b02b5e4bf359
Timestamp: 1580616434 Timestamp [UCT]: 2020-02-02 04:07:14 Age [y:d:h:m:s]: 04:289:07:16:44
Block: 56844 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1098093 RingCT/type: yes/0
Extra: 013653c64fd50d092ad81156995938f1d8bc26897b36a841b883e4b02b5e4bf35902110000000149b77a3d000000000000000000

1 output(s) for total of 397.789260507000 dcy

stealth address amount amount idx
00: 506b4212f8f8bf93be21fc7b9f1dbaf699525f68f9c32cb75d02d2f568b0c793 397.789260507000 104823 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": 56854, "vin": [ { "gen": { "height": 56844 } } ], "vout": [ { "amount": 397789260507, "target": { "key": "506b4212f8f8bf93be21fc7b9f1dbaf699525f68f9c32cb75d02d2f568b0c793" } } ], "extra": [ 1, 54, 83, 198, 79, 213, 13, 9, 42, 216, 17, 86, 153, 89, 56, 241, 216, 188, 38, 137, 123, 54, 168, 65, 184, 131, 228, 176, 43, 94, 75, 243, 89, 2, 17, 0, 0, 0, 1, 73, 183, 122, 61, 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