Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 98907acbac4f6da49546e228d8574ef1f82feb4f72436c0c58dba04c761643bf

Tx prefix hash: 8f297591458474b706e9a4d1c55bb4f7787b248c418127d6389d84954394c097
Tx public key: 332e9b1f1329d75d3fdaf83408cf5c78b47fe0bab1ee9498d84db09c52316302
Timestamp: 1580266702 Timestamp [UCT]: 2020-01-29 02:58:22 Age [y:d:h:m:s]: 05:255:06:13:25
Block: 54611 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1331451 RingCT/type: yes/0
Extra: 01332e9b1f1329d75d3fdaf83408cf5c78b47fe0bab1ee9498d84db09c52316302021100000001b221b3d1000000000000000000

1 output(s) for total of 404.624255317000 dcy

stealth address amount amount idx
00: 1aee1ab31726a63bac0cbe6feea2aabdbfe0cb1a2ba2fc0ec7c8642e6db0a56c 404.624255317000 101052 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": 54621, "vin": [ { "gen": { "height": 54611 } } ], "vout": [ { "amount": 404624255317, "target": { "key": "1aee1ab31726a63bac0cbe6feea2aabdbfe0cb1a2ba2fc0ec7c8642e6db0a56c" } } ], "extra": [ 1, 51, 46, 155, 31, 19, 41, 215, 93, 63, 218, 248, 52, 8, 207, 92, 120, 180, 127, 224, 186, 177, 238, 148, 152, 216, 77, 176, 156, 82, 49, 99, 2, 2, 17, 0, 0, 0, 1, 178, 33, 179, 209, 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