Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf8ccb86c550d949b0eafe36642bf9465c88313ffe763a069af347a8b8be74c8

Tx prefix hash: 5033f4982356905d3e403c54e8e1cde2db1644569f0e1b0378f2a362319514ea
Tx public key: 17a4528ca4381e17cae4cc06dcf6a1728e760ad0d93e07df799f0f8fe89ad030
Timestamp: 1617018319 Timestamp [UCT]: 2021-03-29 11:45:19 Age [y:d:h:m:s]: 03:222:11:36:21
Block: 228955 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 918439 RingCT/type: yes/0
Extra: 0117a4528ca4381e17cae4cc06dcf6a1728e760ad0d93e07df799f0f8fe89ad03002110000011aa9e81d35000000000000000000

1 output(s) for total of 106.998483983000 dcy

stealth address amount amount idx
00: 44648730e45793e6452d653440c0bea52d7fe709d2d18aecff9b0e1b23667073 106.998483983000 475011 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": 228965, "vin": [ { "gen": { "height": 228955 } } ], "vout": [ { "amount": 106998483983, "target": { "key": "44648730e45793e6452d653440c0bea52d7fe709d2d18aecff9b0e1b23667073" } } ], "extra": [ 1, 23, 164, 82, 140, 164, 56, 30, 23, 202, 228, 204, 6, 220, 246, 161, 114, 142, 118, 10, 208, 217, 62, 7, 223, 121, 159, 15, 143, 232, 154, 208, 48, 2, 17, 0, 0, 1, 26, 169, 232, 29, 53, 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