Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 74d71835411d290d6b9124ce09b8e9ae6a11689e349f60c2c58f4c2a89882782

Tx prefix hash: 054a178f81f91f0adfb40aed937df16708f45621602a10f7e0f9076141929525
Tx public key: 6151505bd278e0671a25c6a3d1e9248f3dfe615771d390c30b0595691ac91ca0
Timestamp: 1722725154 Timestamp [UCT]: 2024-08-03 22:45:54 Age [y:d:h:m:s]: 00:173:11:14:33
Block: 1080146 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 124061 RingCT/type: yes/0
Extra: 016151505bd278e0671a25c6a3d1e9248f3dfe615771d390c30b0595691ac91ca0021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4bc387354dc8a5a7926c3f6f42e4a12989e28986a4405fdce84ef2c72fa654eb 0.600000000000 1553395 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": 1080156, "vin": [ { "gen": { "height": 1080146 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4bc387354dc8a5a7926c3f6f42e4a12989e28986a4405fdce84ef2c72fa654eb" } } ], "extra": [ 1, 97, 81, 80, 91, 210, 120, 224, 103, 26, 37, 198, 163, 209, 233, 36, 143, 61, 254, 97, 87, 113, 211, 144, 195, 11, 5, 149, 105, 26, 201, 28, 160, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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