Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d5149bdc4e852857534d1ff338138af4942af948b097df521e8357f086c6c794

Tx prefix hash: d8165d92733e9891302a2e7247e32fca7c28372e95bbabd1a461e9399b427e28
Tx public key: 8b1fbe80a88c3dcf881b78fd0ba858d8a0e4fa23725481050b9d68f5511ae6dc
Timestamp: 1647044904 Timestamp [UCT]: 2022-03-12 00:28:24 Age [y:d:h:m:s]: 03:047:23:47:44
Block: 456464 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 814471 RingCT/type: yes/0
Extra: 018b1fbe80a88c3dcf881b78fd0ba858d8a0e4fa23725481050b9d68f5511ae6dc021100000001d3fcec30000000000000000000

1 output(s) for total of 18.860167701000 dcy

stealth address amount amount idx
00: 6416e975f6d0a663c7f92b8378a8a5c9b4cc64fea4b75b65b28ebbe9df01b6d3 18.860167701000 872527 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": 456474, "vin": [ { "gen": { "height": 456464 } } ], "vout": [ { "amount": 18860167701, "target": { "key": "6416e975f6d0a663c7f92b8378a8a5c9b4cc64fea4b75b65b28ebbe9df01b6d3" } } ], "extra": [ 1, 139, 31, 190, 128, 168, 140, 61, 207, 136, 27, 120, 253, 11, 168, 88, 216, 160, 228, 250, 35, 114, 84, 129, 5, 11, 157, 104, 245, 81, 26, 230, 220, 2, 17, 0, 0, 0, 1, 211, 252, 236, 48, 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