Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: be2ac6a896cbb2d7ea503ba9ceb0b70c4f767852258259620bebc1319e9a9793

Tx prefix hash: 106b7d3b54367d47952a3e651b62b7733d91be9e535a1d0ffb329391db7bc8ee
Tx public key: be3937e9a4921f9a180729fd2ee067bde2bd9ca0134dbd3ac0d533b2f412230e
Timestamp: 1713265340 Timestamp [UCT]: 2024-04-16 11:02:20 Age [y:d:h:m:s]: 00:358:00:05:44
Block: 1001699 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 255967 RingCT/type: yes/0
Extra: 01be3937e9a4921f9a180729fd2ee067bde2bd9ca0134dbd3ac0d533b2f412230e0211000000070011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 51d605e718278dba9cb7ebf8faa5da770eb037e52f53720aa77787832b0e8e54 0.600000000000 1462207 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": 1001709, "vin": [ { "gen": { "height": 1001699 } } ], "vout": [ { "amount": 600000000, "target": { "key": "51d605e718278dba9cb7ebf8faa5da770eb037e52f53720aa77787832b0e8e54" } } ], "extra": [ 1, 190, 57, 55, 233, 164, 146, 31, 154, 24, 7, 41, 253, 46, 224, 103, 189, 226, 189, 156, 160, 19, 77, 189, 58, 192, 213, 51, 178, 244, 18, 35, 14, 2, 17, 0, 0, 0, 7, 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