Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bbc3fa6949dad1747e93660e42e02747ac733ae1b06f98da074c5e134f0f70f0

Tx prefix hash: 3562b19992d629b0efbeea8c5178ad51919e57e1ca33e5d5ef17b5b42ec5ff81
Tx public key: 9e4f7787b46199a0178d5e91de54fe146fe4f06afb1c4855f42fa7d8356fd1cb
Timestamp: 1722564034 Timestamp [UCT]: 2024-08-02 02:00:34 Age [y:d:h:m:s]: 00:089:01:17:50
Block: 1078812 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 63718 RingCT/type: yes/0
Extra: 019e4f7787b46199a0178d5e91de54fe146fe4f06afb1c4855f42fa7d8356fd1cb02110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 950cfa08984da9f1e7e69b4299e03e772fcee0eb6fc02c5a82d672981efea734 0.600000000000 1551503 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": 1078822, "vin": [ { "gen": { "height": 1078812 } } ], "vout": [ { "amount": 600000000, "target": { "key": "950cfa08984da9f1e7e69b4299e03e772fcee0eb6fc02c5a82d672981efea734" } } ], "extra": [ 1, 158, 79, 119, 135, 180, 97, 153, 160, 23, 141, 94, 145, 222, 84, 254, 20, 111, 228, 240, 106, 251, 28, 72, 85, 244, 47, 167, 216, 53, 111, 209, 203, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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