Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5317dc1d237540750c5fad6154e8b96a70c8f921e23c79e0a5ae1df13cbaf7fc

Tx prefix hash: 38666e8b6aa5b30967c0a3e3f579cd3185364ca6f6561307dee58d0075784973
Tx public key: 4f6867794f675baa3d2585da79f2d70a35b93e9aad72931c5da032d943dfd905
Timestamp: 1578896858 Timestamp [UCT]: 2020-01-13 06:27:38 Age [y:d:h:m:s]: 05:071:23:02:40
Block: 44411 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1201630 RingCT/type: yes/0
Extra: 014f6867794f675baa3d2585da79f2d70a35b93e9aad72931c5da032d943dfd90502110000000a4943cd9f000000000000000000

1 output(s) for total of 437.377319992000 dcy

stealth address amount amount idx
00: aa318a8f08cbc90b8eae60a35952f750b3630dcb7802dcecbdc42c810c76661c 437.377319992000 80805 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": 44421, "vin": [ { "gen": { "height": 44411 } } ], "vout": [ { "amount": 437377319992, "target": { "key": "aa318a8f08cbc90b8eae60a35952f750b3630dcb7802dcecbdc42c810c76661c" } } ], "extra": [ 1, 79, 104, 103, 121, 79, 103, 91, 170, 61, 37, 133, 218, 121, 242, 215, 10, 53, 185, 62, 154, 173, 114, 147, 28, 93, 160, 50, 217, 67, 223, 217, 5, 2, 17, 0, 0, 0, 10, 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