Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3aed5fac48526de1bd4d20d3fa1ca27187b152f0b928054682fddc6d6cacea3f

Tx prefix hash: c1294db4b84ad5a2cf8cd53f82f2cc5b2c76132653d55016c068a3ac6b4e1f3a
Tx public key: c358ed25d762f9d3525755d4ab15c8561f4a4b243337edb4f075f880157571b8
Timestamp: 1734347272 Timestamp [UCT]: 2024-12-16 11:07:52 Age [y:d:h:m:s]: 00:136:06:14:05
Block: 1176410 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 97172 RingCT/type: yes/0
Extra: 01c358ed25d762f9d3525755d4ab15c8561f4a4b243337edb4f075f880157571b8021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 86c2a4f9c8cafccfd7ed9529d2e2404e0bc3f010fcc51304ae3e3f461b0682d9 0.600000000000 1662743 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": 1176420, "vin": [ { "gen": { "height": 1176410 } } ], "vout": [ { "amount": 600000000, "target": { "key": "86c2a4f9c8cafccfd7ed9529d2e2404e0bc3f010fcc51304ae3e3f461b0682d9" } } ], "extra": [ 1, 195, 88, 237, 37, 215, 98, 249, 211, 82, 87, 85, 212, 171, 21, 200, 86, 31, 74, 75, 36, 51, 55, 237, 180, 240, 117, 248, 128, 21, 117, 113, 184, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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