Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0fefb1852ab99c7b085f9bcda5ba04a04ff191cf56f5892efa56ad5620f1d7ca

Tx prefix hash: 3b77e704f8d423677dba5d617ee388a1b67fa1567d8569381f9d81dfb0d89176
Tx public key: 97e1b6c45c028d1749b2bf67e177ee84cecc477a13161ae984daaa1d6e361b9c
Timestamp: 1717811840 Timestamp [UCT]: 2024-06-08 01:57:20 Age [y:d:h:m:s]: 00:169:12:14:51
Block: 1039416 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 121322 RingCT/type: yes/0
Extra: 0197e1b6c45c028d1749b2bf67e177ee84cecc477a13161ae984daaa1d6e361b9c02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7ba7238dbe262cbca25db9bb969231a5ff835859004e0dbdafccc3e85f68c51a 0.600000000000 1508055 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": 1039426, "vin": [ { "gen": { "height": 1039416 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7ba7238dbe262cbca25db9bb969231a5ff835859004e0dbdafccc3e85f68c51a" } } ], "extra": [ 1, 151, 225, 182, 196, 92, 2, 141, 23, 73, 178, 191, 103, 225, 119, 238, 132, 206, 204, 71, 122, 19, 22, 26, 233, 132, 218, 170, 29, 110, 54, 27, 156, 2, 17, 0, 0, 0, 1, 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