Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7906dff60fda97ef74c69529ef3da0f45f8dfd710b05f77bcb47da2361d7d261

Tx prefix hash: 3efc39422c99bc5cab50a1dfabd85dab9abb44af05ad3aaecd9548f7015bacc8
Tx public key: 9d49b8fdda77162cab3bcb460527498d49d87e2c718601ea812a9c87b3aaf96d
Timestamp: 1737860159 Timestamp [UCT]: 2025-01-26 02:55:59 Age [y:d:h:m:s]: 00:142:16:19:44
Block: 1205420 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101729 RingCT/type: yes/0
Extra: 019d49b8fdda77162cab3bcb460527498d49d87e2c718601ea812a9c87b3aaf96d021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 98bfeb0602cd6d8622e93238e9804adb9f0b35455144a338c1c2ff5ee3e21cee 0.600000000000 1692117 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": 1205430, "vin": [ { "gen": { "height": 1205420 } } ], "vout": [ { "amount": 600000000, "target": { "key": "98bfeb0602cd6d8622e93238e9804adb9f0b35455144a338c1c2ff5ee3e21cee" } } ], "extra": [ 1, 157, 73, 184, 253, 218, 119, 22, 44, 171, 59, 203, 70, 5, 39, 73, 141, 73, 216, 126, 44, 113, 134, 1, 234, 129, 42, 156, 135, 179, 170, 249, 109, 2, 17, 0, 0, 0, 7, 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