Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b700fbfc68fb0ba2e00267b4a074c4d0437200eabe945d84e9058c90ae7c0f2d

Tx prefix hash: cabc1c5197d19ea4468d89186c52d59d38b6c842380ede9435ce1541de902606
Tx public key: 0c0b6d5df1df2420cbdbe553f148f5b121d3ecc8202386a26b5b346aad523f41
Timestamp: 1720946777 Timestamp [UCT]: 2024-07-14 08:46:17 Age [y:d:h:m:s]: 01:086:19:34:22
Block: 1065417 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 320509 RingCT/type: yes/0
Extra: 010c0b6d5df1df2420cbdbe553f148f5b121d3ecc8202386a26b5b346aad523f4102110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b20619c5980de220dfc2daf8caea77c7747006db4bad86b1eb322ead7f69bef3 0.600000000000 1535962 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": 1065427, "vin": [ { "gen": { "height": 1065417 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b20619c5980de220dfc2daf8caea77c7747006db4bad86b1eb322ead7f69bef3" } } ], "extra": [ 1, 12, 11, 109, 93, 241, 223, 36, 32, 203, 219, 229, 83, 241, 72, 245, 177, 33, 211, 236, 200, 32, 35, 134, 162, 107, 91, 52, 106, 173, 82, 63, 65, 2, 17, 0, 0, 0, 7, 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