Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5eebddf42c8b93d610b6b4a6f636877db1226f27269ecc755a369a62e676b971

Tx prefix hash: 326f4a4d20646a8f878f56150ae138959bab1c6cd21966e89991d15bde564be3
Tx public key: 70adb2a83ceb1cead920a4afb43a1f76cb8dbf9ec8895cecebfb03bcf9d4dea9
Timestamp: 1737057273 Timestamp [UCT]: 2025-01-16 19:54:33 Age [y:d:h:m:s]: 00:057:03:26:36
Block: 1198821 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 40623 RingCT/type: yes/0
Extra: 0170adb2a83ceb1cead920a4afb43a1f76cb8dbf9ec8895cecebfb03bcf9d4dea9021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 169b6049bcdc90fd979320b9267f179d12a2d8e7e5857689663b40ba3d513f2b 0.600000000000 1685448 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": 1198831, "vin": [ { "gen": { "height": 1198821 } } ], "vout": [ { "amount": 600000000, "target": { "key": "169b6049bcdc90fd979320b9267f179d12a2d8e7e5857689663b40ba3d513f2b" } } ], "extra": [ 1, 112, 173, 178, 168, 60, 235, 28, 234, 217, 32, 164, 175, 180, 58, 31, 118, 203, 141, 191, 158, 200, 137, 92, 236, 235, 251, 3, 188, 249, 212, 222, 169, 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