Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e1dc547b1ce5d6f9a9135a7ee421ecc11a66333f5a40d242a30e7882c1d30bdc

Tx prefix hash: c825249ef4f78315a970a6aabe3065d7309cbc0d03bb673eb947605f77d953a6
Tx public key: b1c035ecaaee49631ed23930c233e8504f04a64281773df9ba8636670ee55abc
Timestamp: 1577701081 Timestamp [UCT]: 2019-12-30 10:18:01 Age [y:d:h:m:s]: 05:111:18:27:11
Block: 34933 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1229685 RingCT/type: yes/0
Extra: 01b1c035ecaaee49631ed23930c233e8504f04a64281773df9ba8636670ee55abc021100000171c3a1a09f000000000000000000

1 output(s) for total of 470.168278559000 dcy

stealth address amount amount idx
00: abe72ae724d4936b94cab34ed650b51869f843e3e16d9520cfcac3e1fe8d66e2 470.168278559000 58850 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": 34943, "vin": [ { "gen": { "height": 34933 } } ], "vout": [ { "amount": 470168278559, "target": { "key": "abe72ae724d4936b94cab34ed650b51869f843e3e16d9520cfcac3e1fe8d66e2" } } ], "extra": [ 1, 177, 192, 53, 236, 170, 238, 73, 99, 30, 210, 57, 48, 194, 51, 232, 80, 79, 4, 166, 66, 129, 119, 61, 249, 186, 134, 54, 103, 14, 229, 90, 188, 2, 17, 0, 0, 1, 113, 195, 161, 160, 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