Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1b35ac8c93fe1761d626e4de6c32042518c0b1d2a88f674b175ade64eec6e9f0

Tx prefix hash: b45f6b3ac9ad26b8b76939d1ad7de45df22ac8a5f32fd5930aa1aae5da3a77d0
Tx public key: ab641fa21f0d645803c61acab6992b10af271b33ae88ae6116a973b4c684048b
Timestamp: 1577742866 Timestamp [UCT]: 2019-12-30 21:54:26 Age [y:d:h:m:s]: 05:004:19:01:41
Block: 35346 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1153373 RingCT/type: yes/0
Extra: 01ab641fa21f0d645803c61acab6992b10af271b33ae88ae6116a973b4c684048b02110000000bd81c26c0000000000000000000

1 output(s) for total of 468.689132482000 dcy

stealth address amount amount idx
00: 3da89ae59c5c729827240c6aa1f58d12fdbe8c3092e92f8fc687064aba92cc85 468.689132482000 59544 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": 35356, "vin": [ { "gen": { "height": 35346 } } ], "vout": [ { "amount": 468689132482, "target": { "key": "3da89ae59c5c729827240c6aa1f58d12fdbe8c3092e92f8fc687064aba92cc85" } } ], "extra": [ 1, 171, 100, 31, 162, 31, 13, 100, 88, 3, 198, 26, 202, 182, 153, 43, 16, 175, 39, 27, 51, 174, 136, 174, 97, 22, 169, 115, 180, 198, 132, 4, 139, 2, 17, 0, 0, 0, 11, 216, 28, 38, 192, 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