Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 637153f7ef41c232bcf9e22a11ab35b2128e76fdae4e6080e61bf35c66d8bbed

Tx prefix hash: 808df40d08f46d2b61e9bbd805f498c07ba1a93df69741223d3ba641ea8b9ba3
Tx public key: 82648280dbda4ab9238fb8c6c7ebf2afb4188f721f22cff36ae8a4e9ec833238
Timestamp: 1705218125 Timestamp [UCT]: 2024-01-14 07:42:05 Age [y:d:h:m:s]: 01:066:11:27:44
Block: 934983 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 308629 RingCT/type: yes/0
Extra: 0182648280dbda4ab9238fb8c6c7ebf2afb4188f721f22cff36ae8a4e9ec8332380211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 51c0bfe0fa7cd102181b0b53370aa3f589a9e39f72a15c815284ad44bcac1962 0.600000000000 1392999 of 15

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": 934993, "vin": [ { "gen": { "height": 934983 } } ], "vout": [ { "amount": 600000000, "target": { "key": "51c0bfe0fa7cd102181b0b53370aa3f589a9e39f72a15c815284ad44bcac1962" } } ], "extra": [ 1, 130, 100, 130, 128, 219, 218, 74, 185, 35, 143, 184, 198, 199, 235, 242, 175, 180, 24, 143, 114, 31, 34, 207, 243, 106, 232, 164, 233, 236, 131, 50, 56, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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