Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 44e8283d17d7d649ec63047d29e44aa026f9ef1b3794e4442c83d992b9bf1a12

Tx prefix hash: 332fed490e9f39a3a38c6ccddcdb916e91a120f218dd7f04c9a1b3a712a23cb6
Tx public key: 1160eaa0baef2ffd5fb6ab7b7fee4e413baed70481ef1ef062729a3f6e74663a
Timestamp: 1580885883 Timestamp [UCT]: 2020-02-05 06:58:03 Age [y:d:h:m:s]: 05:071:18:14:59
Block: 58842 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1203534 RingCT/type: yes/0
Extra: 011160eaa0baef2ffd5fb6ab7b7fee4e413baed70481ef1ef062729a3f6e74663a02110000000149b77a3d000000000000000000

1 output(s) for total of 391.771507344000 dcy

stealth address amount amount idx
00: 06370fefa9879967efa2ef67d25b815bf4ac869c17b10d49a8a1af7bd706f351 391.771507344000 108764 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": 58852, "vin": [ { "gen": { "height": 58842 } } ], "vout": [ { "amount": 391771507344, "target": { "key": "06370fefa9879967efa2ef67d25b815bf4ac869c17b10d49a8a1af7bd706f351" } } ], "extra": [ 1, 17, 96, 234, 160, 186, 239, 47, 253, 95, 182, 171, 123, 127, 238, 78, 65, 59, 174, 215, 4, 129, 239, 30, 240, 98, 114, 154, 63, 110, 116, 102, 58, 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