Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f00dfd2e880bcbac81772a9ebfb8cc6760b4cdba85f9b50f5025ee810f83a055

Tx prefix hash: e7eaeb1ef3e8440090e7cb9c5c8cd0d932af6384dc8daf98391933c35194cc11
Tx public key: d533790e0f2c9de333cc21c7ea79817333db1b452a0508e9fcd0ed716076614a
Timestamp: 1719723657 Timestamp [UCT]: 2024-06-30 05:00:57 Age [y:d:h:m:s]: 00:319:03:47:07
Block: 1055258 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 228085 RingCT/type: yes/0
Extra: 01d533790e0f2c9de333cc21c7ea79817333db1b452a0508e9fcd0ed716076614a02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3dd3d4a34c147d96e3c5a01d5cc2cac0ddfe1ad1624979d70d2fd457345fd3a8 0.600000000000 1525655 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": 1055268, "vin": [ { "gen": { "height": 1055258 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3dd3d4a34c147d96e3c5a01d5cc2cac0ddfe1ad1624979d70d2fd457345fd3a8" } } ], "extra": [ 1, 213, 51, 121, 14, 15, 44, 157, 227, 51, 204, 33, 199, 234, 121, 129, 115, 51, 219, 27, 69, 42, 5, 8, 233, 252, 208, 237, 113, 96, 118, 97, 74, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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