Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0fbce270e47bdf4d19e02a1cabd7b638ed5e425faa8c06e2f57e9aa5ed370337

Tx prefix hash: c78b7a86c815f1686f6fe3d5dddc1adc4ddd896433909b16299ee81f4f5716f0
Tx public key: 085eb50bf3456a57e5333f01521c91553f6da9aea4f65cf6682c1534436140b3
Timestamp: 1634246089 Timestamp [UCT]: 2021-10-14 21:14:49 Age [y:d:h:m:s]: 03:211:14:19:02
Block: 353114 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 928880 RingCT/type: yes/0
Extra: 01085eb50bf3456a57e5333f01521c91553f6da9aea4f65cf6682c1534436140b302110000001b5410958b000000000000000000

1 output(s) for total of 41.494176739000 dcy

stealth address amount amount idx
00: fd2a403ad7c6a5d5e8b6a2c05df27aa75b0e60c4b7c59eef8b28e5796779c801 41.494176739000 721624 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": 353124, "vin": [ { "gen": { "height": 353114 } } ], "vout": [ { "amount": 41494176739, "target": { "key": "fd2a403ad7c6a5d5e8b6a2c05df27aa75b0e60c4b7c59eef8b28e5796779c801" } } ], "extra": [ 1, 8, 94, 181, 11, 243, 69, 106, 87, 229, 51, 63, 1, 82, 28, 145, 85, 63, 109, 169, 174, 164, 246, 92, 246, 104, 44, 21, 52, 67, 97, 64, 179, 2, 17, 0, 0, 0, 27, 84, 16, 149, 139, 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