Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4bf8019744719c8b151a993759ee5b422a6f18471cc9134a4760c548d8132259

Tx prefix hash: b8a1ace6422488a17f9947c27a1459262e73e8f63454f9ce0e22e3d99574a43f
Tx public key: 4a045f1a7e9012fe101cba00ecfb85f4306b604f85fcf95b4f1939e84ef19b28
Timestamp: 1695618493 Timestamp [UCT]: 2023-09-25 05:08:13 Age [y:d:h:m:s]: 01:153:13:24:07
Block: 855622 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 370775 RingCT/type: yes/0
Extra: 014a045f1a7e9012fe101cba00ecfb85f4306b604f85fcf95b4f1939e84ef19b280211000000034b8f5122000000000000000000

1 output(s) for total of 0.897365104000 dcy

stealth address amount amount idx
00: a10f2d866df0f2561f24efd7e76fd9f7988ee7ed334282b25736ab0f1a9bfbbb 0.897365104000 1309652 of 0

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": 855632, "vin": [ { "gen": { "height": 855622 } } ], "vout": [ { "amount": 897365104, "target": { "key": "a10f2d866df0f2561f24efd7e76fd9f7988ee7ed334282b25736ab0f1a9bfbbb" } } ], "extra": [ 1, 74, 4, 95, 26, 126, 144, 18, 254, 16, 28, 186, 0, 236, 251, 133, 244, 48, 107, 96, 79, 133, 252, 249, 91, 79, 25, 57, 232, 78, 241, 155, 40, 2, 17, 0, 0, 0, 3, 75, 143, 81, 34, 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