Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 34170a4d7824826a7a2811682c6419f2a5eb84d0b85dc3510e6c2e26bab9adcd

Tx prefix hash: 16422d469f17bd02843be063f9c1a4e2fcca72de880e3ad0b052e3eb589054e4
Tx public key: 9033bac2e53004a8ed8b3c801974f5acde68237c1cb4768fdf9297c105e62370
Timestamp: 1728039132 Timestamp [UCT]: 2024-10-04 10:52:12 Age [y:d:h:m:s]: 00:223:14:03:56
Block: 1124208 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 159609 RingCT/type: yes/0
Extra: 019033bac2e53004a8ed8b3c801974f5acde68237c1cb4768fdf9297c105e62370021100000001e914dd15000000000000000000

1 output(s) for total of 0.616050000000 dcy

stealth address amount amount idx
00: 43b78c4d812b06bce73dce1c4138c29b87aea36e896c0f164bdeacb826d7d2c6 0.616050000000 1606799 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": 1124218, "vin": [ { "gen": { "height": 1124208 } } ], "vout": [ { "amount": 616050000, "target": { "key": "43b78c4d812b06bce73dce1c4138c29b87aea36e896c0f164bdeacb826d7d2c6" } } ], "extra": [ 1, 144, 51, 186, 194, 229, 48, 4, 168, 237, 139, 60, 128, 25, 116, 245, 172, 222, 104, 35, 124, 28, 180, 118, 143, 223, 146, 151, 193, 5, 230, 35, 112, 2, 17, 0, 0, 0, 1, 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